Skip to content

[core] Handle 429 and 500 errors from worlds in runtime #966

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
VaguelySerious merged 12 commits into from
Feb 9, 2026
Merged

[core] Handle 429 and 500 errors from worlds in runtime #966

VaguelySerious merged 12 commits into from
Feb 9, 2026

Conversation

@VaguelySerious
Copy link
Member

@VaguelySerious VaguelySerious commented Feb 6, 2026 •
edited
Loading

Uses retry-after header for 429 when provided.
500s are limited to 3x retry, doing exponential backoff.

Review with white space off for sanity.

Claude's suggestion for e2e tests, which I think we might do separately. I think we should make some sort of testbench for world errors and how the runtime reacts.

  3. E2E with a fault-injection endpoint (moderate effort, very targeted)

  Add a test-only endpoint to the workbench app (or a middleware) that can be told to return 429/500 for the next N requests. Something like:

  POST /e2e/inject-fault { status: 429, retryAfter: 3, count: 2 }

  Then the e2e test would:
  1. Inject a fault (e.g. "next 2 requests to workflow handler return 429 with Retry-After: 3")
  2. Start a workflow
  3. Assert it completes successfully despite the transient errors
  4. Optionally check logs/traces for the retry events

  This is the most surgical approach but requires adding test-only infrastructure. The world-local queue already makes HTTP requests to the app endpoints, so you could intercept at that
  layer.

@VaguelySerious
changes
8764b75 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@changeset-bot
Copy link

changeset-bot bot commented Feb 6, 2026 •
edited
Loading

🦋 Changeset detected

Latest commit: 9f75d33

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 19 packages
Name Type
@workflow/errors Patch
@workflow/world Patch
@workflow/world-vercel Patch
@workflow/core Patch
@workflow/builders Patch
@workflow/cli Patch
workflow Patch
@workflow/world-local Patch
@workflow/world-postgres Patch
@workflow/web-shared Patch
@workflow/world-testing Patch
@workflow/next Patch
@workflow/nitro Patch
@workflow/astro Patch
@workflow/nest Patch
@workflow/rollup Patch
@workflow/sveltekit Patch
@workflow/vite Patch
@workflow/nuxt Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel
Copy link
Contributor

vercel bot commented Feb 6, 2026 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
example-nextjs-workflow-turbopack Ready Ready Preview, Comment, Open in v0 Feb 9, 2026 10:23pm
example-nextjs-workflow-webpack Ready Ready Preview, Comment, Open in v0 Feb 9, 2026 10:23pm
example-workflow Ready Ready Preview, Comment, Open in v0 Feb 9, 2026 10:23pm
workbench-astro-workflow Ready Ready Preview, Comment, Open in v0 Feb 9, 2026 10:23pm
workbench-express-workflow Ready Ready Preview, Comment, Open in v0 Feb 9, 2026 10:23pm
workbench-fastify-workflow Ready Ready Preview, Comment, Open in v0 Feb 9, 2026 10:23pm
workbench-hono-workflow Ready Ready Preview, Comment, Open in v0 Feb 9, 2026 10:23pm
workbench-nitro-workflow Ready Ready Preview, Comment, Open in v0 Feb 9, 2026 10:23pm
workbench-nuxt-workflow Ready Ready Preview, Comment, Open in v0 Feb 9, 2026 10:23pm
workbench-sveltekit-workflow Ready Ready Preview, Comment, Open in v0 Feb 9, 2026 10:23pm
workbench-vite-workflow Ready Ready Preview, Comment, Open in v0 Feb 9, 2026 10:23pm
workflow-docs Ready Ready Preview, Comment, Open in v0 Feb 9, 2026 10:23pm
workflow-nest Ready Ready Preview, Comment, Open in v0 Feb 9, 2026 10:23pm
workflow-swc-playground Ready Ready Preview, Comment, Open in v0 Feb 9, 2026 10:23pm

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026 •
edited
Loading

🧪 E2E Test Results

❌ Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 490 0 38 528
✅ 💻 Local Development 418 0 62 480
✅ 📦 Local Production 418 0 62 480
✅ 🐘 Local Postgres 418 0 62 480
✅ 🪟 Windows 45 0 3 48
❌ 🌍 Community Worlds 105 42 9 156
✅ 📋 Other 123 0 21 144
Total 2017 42 257 2316

❌ Failed Tests

🌍 Community Worlds (42 failed)

mongodb (1 failed):

  • webhookWorkflow

turso (41 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
App Passed Failed Skipped
✅ astro 44 0 4
✅ example 44 0 4
✅ express 44 0 4
✅ fastify 44 0 4
✅ hono 44 0 4
✅ nextjs-turbopack 47 0 1
✅ nextjs-webpack 47 0 1
✅ nitro 44 0 4
✅ nuxt 44 0 4
✅ sveltekit 44 0 4
✅ vite 44 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
✅ nextjs-turbopack-stable 45 0 3
✅ nextjs-webpack-stable 45 0 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
✅ nextjs-turbopack-stable 45 0 3
✅ nextjs-webpack-stable 45 0 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
✅ nextjs-turbopack-stable 45 0 3
✅ nextjs-webpack-stable 45 0 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 45 0 3
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
❌ mongodb 44 1 3
✅ redis-dev 3 0 0
✅ redis 45 0 3
✅ starter-dev 3 0 0
✅ turso-dev 3 0 0
❌ turso 4 41 3
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 41 0 7
✅ e2e-local-postgres-nest-stable 41 0 7
✅ e2e-local-prod-nest-stable 41 0 7

📋 View full workflow run

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026 •
edited
Loading

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 0.032s (+22.9% 🔺) 1.005s (~) 0.973s 10 1.00x
💻 Local Express 0.032s (-2.7%) 1.005s (~) 0.973s 10 1.02x
💻 Local Next.js (Turbopack) 0.046s 1.005s 0.959s 10 1.44x
🌐 Redis Next.js (Turbopack) 0.051s 1.005s 0.953s 10 1.62x
🐘 Postgres Nitro 0.106s (+13.5% 🔺) 1.009s (~) 0.903s 10 3.36x
🌐 MongoDB Next.js (Turbopack) 0.110s 1.007s 0.897s 10 3.48x
🐘 Postgres Express 0.194s (-45.0% 🟢) 1.021s (-2.1%) 0.827s 10 6.12x
🐘 Postgres Next.js (Turbopack) 0.444s 1.009s 0.565s 10 14.01x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 0.784s (-7.5% 🟢) 2.468s (-4.7%) 1.684s 10 1.00x
▲ Vercel Next.js (Turbopack) 0.786s (-14.1% 🟢) 2.385s (-1.5%) 1.599s 10 1.00x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.105s 2.006s 0.901s 10 1.00x
💻 Local Nitro 1.105s (+2.8%) 2.006s (~) 0.901s 10 1.00x
💻 Local Express 1.108s (~) 2.006s (~) 0.898s 10 1.00x
🌐 Redis Next.js (Turbopack) 1.110s 2.006s 0.896s 10 1.00x
🌐 MongoDB Next.js (Turbopack) 1.300s 2.007s 0.707s 10 1.18x
🐘 Postgres Next.js (Turbopack) 1.907s 2.113s 0.206s 10 1.73x
🐘 Postgres Express 2.460s (+10.6% 🔺) 3.014s (~) 0.554s 10 2.23x
🐘 Postgres Nitro 2.500s (+27.1% 🔺) 3.013s (+36.1% 🔺) 0.513s 10 2.26x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.957s (+12.5% 🔺) 3.946s (+7.1% 🔺) 0.988s 10 1.00x
▲ Vercel Express 3.215s (+22.0% 🔺) 4.569s (+21.6% 🔺) 1.354s 10 1.09x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Express

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 10.722s 11.022s 0.300s 3 1.00x
💻 Local Next.js (Turbopack) 10.745s 11.023s 0.278s 3 1.00x
💻 Local Nitro 10.838s (+2.4%) 11.022s (~) 0.184s 3 1.01x
💻 Local Express 10.839s (~) 11.024s (~) 0.185s 3 1.01x
🌐 MongoDB Next.js (Turbopack) 12.349s 13.025s 0.677s 3 1.15x
🐘 Postgres Next.js (Turbopack) 15.512s 16.049s 0.537s 2 1.45x
🐘 Postgres Express 20.303s (~) 21.061s (~) 0.758s 2 1.89x
🐘 Postgres Nitro 20.372s (+32.8% 🔺) 21.053s (+31.2% 🔺) 0.682s 2 1.90x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 18.895s (-5.9% 🟢) 20.661s (-1.5%) 1.766s 2 1.00x
▲ Vercel Next.js (Turbopack) 21.076s (+8.2% 🔺) 22.174s (+8.3% 🔺) 1.098s 2 1.12x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 26.866s 27.050s 0.185s 3 1.00x
💻 Local Next.js (Turbopack) 27.305s 28.051s 0.746s 3 1.02x
💻 Local Nitro 27.454s (+2.6%) 28.049s (+3.7%) 0.596s 3 1.02x
💻 Local Express 27.557s (~) 28.052s (~) 0.495s 3 1.03x
🌐 MongoDB Next.js (Turbopack) 30.556s 31.046s 0.490s 2 1.14x
🐘 Postgres Nitro 50.218s (+21.3% 🔺) 51.134s (+21.4% 🔺) 0.915s 2 1.87x
🐘 Postgres Express 50.303s (~) 50.630s (-1.0%) 0.327s 2 1.87x
🐘 Postgres Next.js (Turbopack) 50.312s 50.623s 0.312s 2 1.87x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 48.126s (-3.0%) 48.969s (-5.3% 🟢) 0.843s 2 1.00x
▲ Vercel Next.js (Turbopack) 49.886s (-4.5%) 51.786s (-3.7%) 1.900s 2 1.04x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 54.374s 55.101s 0.726s 2 1.00x
💻 Local Next.js (Turbopack) 56.919s 57.103s 0.184s 2 1.05x
💻 Local Nitro 57.120s (+2.8%) 58.098s (+3.6%) 0.978s 2 1.05x
💻 Local Express 57.342s (~) 58.106s (~) 0.764s 2 1.05x
🌐 MongoDB Next.js (Turbopack) 61.157s 61.592s 0.435s 2 1.12x
🐘 Postgres Next.js (Turbopack) 91.740s 92.206s 0.466s 1 1.69x
🐘 Postgres Express 100.159s (~) 100.227s (-1.0%) 0.068s 1 1.84x
🐘 Postgres Nitro 100.479s (+26.0% 🔺) 101.227s (+26.2% 🔺) 0.748s 1 1.85x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 101.457s (-0.6%) 102.618s (-0.8%) 1.161s 1 1.00x
▲ Vercel Next.js (Turbopack) 104.877s (+1.8%) 105.825s (+2.1%) 0.948s 1 1.03x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.254s 2.006s 0.753s 15 1.00x
💻 Local Nitro 1.405s (+4.5%) 2.006s (~) 0.601s 15 1.12x
💻 Local Express 1.416s (~) 2.005s (~) 0.589s 15 1.13x
💻 Local Next.js (Turbopack) 1.432s 2.005s 0.573s 15 1.14x
🐘 Postgres Next.js (Turbopack) 2.095s 2.474s 0.379s 13 1.67x
🌐 MongoDB Next.js (Turbopack) 2.164s 3.008s 0.844s 10 1.73x
🐘 Postgres Express 2.194s (-6.6% 🟢) 3.014s (~) 0.820s 10 1.75x
🐘 Postgres Nitro 2.485s (+40.2% 🔺) 3.014s (+45.0% 🔺) 0.529s 10 1.98x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.728s (+1.1%) 3.889s (+4.9%) 1.161s 8 1.00x
▲ Vercel Express 3.000s (+10.3% 🔺) 4.204s (+9.7% 🔺) 1.204s 8 1.10x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Express

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 2.485s 3.008s 0.523s 10 1.00x
💻 Local Nitro 2.544s (+13.2% 🔺) 3.007s (~) 0.463s 10 1.02x
💻 Local Express 2.619s (+2.4%) 3.007s (~) 0.388s 10 1.05x
💻 Local Next.js (Turbopack) 2.642s 3.007s 0.364s 10 1.06x
🌐 MongoDB Next.js (Turbopack) 4.767s 5.178s 0.411s 6 1.92x
🐘 Postgres Express 8.884s (-0.5%) 9.546s (+2.9%) 0.661s 4 3.58x
🐘 Postgres Nitro 9.960s (-10.4% 🟢) 10.697s (-8.6% 🟢) 0.737s 3 4.01x
🐘 Postgres Next.js (Turbopack) 12.648s 13.037s 0.389s 3 5.09x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.552s (+9.2% 🔺) 5.099s (+14.9% 🔺) 1.547s 6 1.00x
▲ Vercel Express 3.700s (+17.3% 🔺) 5.005s (+20.3% 🔺) 1.305s 7 1.04x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Express

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 4.067s 4.725s 0.658s 7 1.00x
💻 Local Nitro 7.071s (+19.5% 🔺) 7.767s (+21.1% 🔺) 0.696s 4 1.74x
💻 Local Next.js (Turbopack) 7.627s 8.016s 0.390s 4 1.88x
💻 Local Express 7.708s (+5.2% 🔺) 8.273s (+3.2%) 0.565s 4 1.90x
🌐 MongoDB Next.js (Turbopack) 9.877s 10.352s 0.475s 3 2.43x
🐘 Postgres Nitro 50.050s (-4.4%) 50.119s (-5.7% 🟢) 0.069s 1 12.31x
🐘 Postgres Express 51.197s (+8.8% 🔺) 52.128s (+8.4% 🔺) 0.931s 1 12.59x
🐘 Postgres Next.js (Turbopack) 55.317s 56.128s 0.811s 1 13.60x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.682s (-1.3%) 5.309s (+5.1% 🔺) 1.626s 6 1.00x
▲ Vercel Express 4.333s (+22.4% 🔺) 5.927s (+17.6% 🔺) 1.594s 7 1.18x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Express

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.259s 2.006s 0.747s 15 1.00x
💻 Local Nitro 1.425s (+5.2% 🔺) 2.004s (~) 0.580s 15 1.13x
💻 Local Express 1.431s (~) 2.006s (~) 0.574s 15 1.14x
💻 Local Next.js (Turbopack) 1.464s 2.006s 0.542s 15 1.16x
🐘 Postgres Nitro 2.141s (+27.4% 🔺) 2.831s (+36.3% 🔺) 0.691s 11 1.70x
🐘 Postgres Express 2.142s (+2.0%) 2.741s (+5.6% 🔺) 0.599s 11 1.70x
🌐 MongoDB Next.js (Turbopack) 2.169s 3.008s 0.839s 10 1.72x
🐘 Postgres Next.js (Turbopack) 2.308s 2.741s 0.432s 11 1.83x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.631s (+1.9%) 3.817s (-0.8%) 1.186s 8 1.00x
▲ Vercel Next.js (Turbopack) 2.777s (+2.8%) 4.032s (+4.4%) 1.254s 8 1.06x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 2.493s 3.008s 0.515s 10 1.00x
💻 Local Nitro 2.635s (+9.4% 🔺) 3.007s (~) 0.372s 10 1.06x
💻 Local Next.js (Turbopack) 2.722s 3.008s 0.285s 10 1.09x
💻 Local Express 2.837s (+3.1%) 3.008s (~) 0.170s 10 1.14x
🌐 MongoDB Next.js (Turbopack) 4.725s 5.176s 0.451s 6 1.89x
🐘 Postgres Express 11.149s (+2.8%) 11.698s (+2.9%) 0.548s 3 4.47x
🐘 Postgres Nitro 12.296s (+14.2% 🔺) 13.039s (+14.7% 🔺) 0.743s 3 4.93x
🐘 Postgres Next.js (Turbopack) 12.730s 13.368s 0.638s 3 5.11x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.981s (-6.6% 🟢) 4.089s (-0.8%) 1.108s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.066s (-10.0% 🟢) 3.923s (-15.5% 🟢) 0.857s 8 1.03x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 4.079s 4.725s 0.646s 7 1.00x
💻 Local Nitro 7.739s (+16.5% 🔺) 8.016s (+14.3% 🔺) 0.277s 4 1.90x
💻 Local Next.js (Turbopack) 8.017s 8.518s 0.501s 4 1.97x
💻 Local Express 8.163s (+4.8%) 9.023s (+12.5% 🔺) 0.860s 4 2.00x
🌐 MongoDB Next.js (Turbopack) 9.734s 10.348s 0.614s 3 2.39x
🐘 Postgres Nitro 52.679s (+7.4% 🔺) 53.124s (+8.1% 🔺) 0.445s 1 12.91x
🐘 Postgres Next.js (Turbopack) 54.508s 55.127s 0.619s 1 13.36x
🐘 Postgres Express 54.742s (+4.8%) 55.132s (+3.8%) 0.390s 1 13.42x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.188s (-6.3% 🟢) 4.374s (-13.7% 🟢) 1.186s 7 1.00x
▲ Vercel Next.js (Turbopack) 3.623s (-14.2% 🟢) 5.046s (-9.5% 🟢) 1.422s 6 1.14x
▲ Vercel Nitro ⚠️ missing - - - -

🔍 Observability: Express | Next.js (Turbopack)

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 0.147s 1.001s 0.011s 1.016s 0.869s 10 1.00x
🌐 Redis Next.js (Turbopack) 0.148s 1.000s 0.001s 1.007s 0.859s 10 1.00x
💻 Local Nitro 0.173s (+55.5% 🔺) 1.002s (~) 0.010s (+14.6% 🔺) 1.015s (~) 0.842s 10 1.17x
💻 Local Express 0.175s (~) 1.002s (~) 0.011s (+9.1% 🔺) 1.016s (~) 0.841s 10 1.19x
🌐 MongoDB Next.js (Turbopack) 0.496s 0.951s 0.001s 1.009s 0.513s 10 3.37x
🐘 Postgres Next.js (Turbopack) 1.459s 1.650s 0.001s 2.012s 0.553s 10 9.90x
🐘 Postgres Nitro 2.144s (+68.7% 🔺) 2.900s (+63.8% 🔺) 0.001s (~) 3.015s (+49.7% 🔺) 0.871s 10 14.54x
🐘 Postgres Express 2.271s (+4.8%) 2.771s (-3.6%) 0.001s (-16.7% 🟢) 3.015s (~) 0.744s 10 15.41x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.396s (-6.6% 🟢) 3.058s (-8.5% 🟢) 0.167s (+8.2% 🔺) 3.971s (-6.6% 🟢) 1.575s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.609s (+8.1% 🔺) 2.867s (-6.0% 🟢) 0.198s (+87.7% 🔺) 3.836s (-0.9%) 1.227s 10 1.09x
▲ Vercel Nitro ⚠️ missing - - - - -

🔍 Observability: Express | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Nitro 7/12
🐘 Postgres Nitro 5/12
▲ Vercel Express 8/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 10/12
Next.js (Turbopack) 🌐 Redis 7/12
Nitro 💻 Local 12/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Starter: Community world (local development)
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

@VaguelySerious @claude
Add 429 throttle retry and 500 server error retry with backoff
fde5d99 
- Propagate Retry-After header as WorkflowAPIError.retryAfter on 429 responses
- Add withThrottleRetry wrapper for both workflow and step handlers
- Re-enqueue workflows on 5xx errors with exponential backoff (5s, 30s, 120min)
- Track serverErrorRetryCount in queue payload for retry budgeting
- Expose delaySeconds on QueueOptions interface

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
vercel[bot]
vercel bot reviewed Feb 9, 2026
View reviewed changes
@VaguelySerious
Fix
9f75d33 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious VaguelySerious merged commit 56f2221 into main Feb 9, 2026
91 of 94 checks passed
@VaguelySerious VaguelySerious deleted the peter/429-core branch February 9, 2026 22:43
@vercel-release-bot vercel-release-bot mentioned this pull request Feb 9, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pranaygp pranaygp pranaygp approved these changes

@vercel vercel[bot] vercel[bot] left review comments

@karthikscale3 karthikscale3 karthikscale3 left review comments

@TooTallNate TooTallNate Awaiting requested review from TooTallNate

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@VaguelySerious @karthikscale3 @pranaygp